FYI I tweaked the PR description to prevent closing the issue just yet. This change addresses the main issue so I wanted to go ahead and get it out ASAP, but there's a few other edge cases I'd like to tweak as well, for example ensuring the page default is something other than master even if any of the API calls fail:

Let me know if you'd be interested in working on that, or really anything else, as there's some other improvements I'd like to see in the config docs as well

The doc page does not appear to honor the version GET parameter (anymore?) For example, browse to https://rust-lang.github.io/rustfmt/?version=master&search=#array_width and observe that after a brief flash of correct content, the selected version resets to 1.4.32, the array_width and other non-1.* sections are hidden, and the browser scroll position becomes incorrect.

The doc page does not appear to honor the version GET parameter (anymore?) For example, browse to https://rust-lang.github.io/rustfmt/?version=master&search=#array_width and observe that after a brief flash of correct content, the selected version resets to 1.4.32, the array_width and other non-1.* sections are hidden, and the browser scroll position becomes incorrect.

@jdahlstrom My bad. I'll try to figure out the cause and find a better way.

Thanks for the report @jdahlstrom!

backported in #4958